Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#129, #162 add ws ping-pong and close if no response #169

Merged
merged 1 commit into from
May 30, 2015
Merged

Conversation

brycekahle
Copy link
Contributor

This utilizes the web socket protocol ping-pong op codes. If the
connection supports them, it will send them instead of heartbeat
frames. If the client doesn’t respond within 10 seconds, it considers
the connection closed.

This utilizes the web socket protocol ping-pong op codes. If the
connection supports them, it will send them instead of heartbeat
frames. If the client doesn’t respond within 10 seconds, it considers
the connection closed.
@brycekahle
Copy link
Contributor Author

I'm going to merge this since nobody has any comments.

brycekahle added a commit that referenced this pull request May 30, 2015
#129, #162 add ws ping-pong and close if no response
@brycekahle brycekahle merged commit c7f9a5f into master May 30, 2015
@brycekahle brycekahle deleted the ws-ping branch May 30, 2015 03:40
@jcheng5
Copy link
Contributor

jcheng5 commented Nov 14, 2016

FYI, we have a customer (for @rstudio/shiny-server) that has reported that when large messages are passed over a slow internet connection using SockJS (taking 1-2 minutes to transfer), then as soon as the message is received the connection is closed with 3000 "No response from heartbeat". Ideally the 10 second timeout timer should not begin until the message is actually sent, not when it is simply queued on the server side (though I don't know how you would implement that on top of faye's API).

In the meantime we've told them to disable the websocket transport as a workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants